home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9706 / 000011_owner-urn-ietf _Wed Jun 4 10:13:46 1997.msg < prev    next >
Internet Message Format  |  1997-06-19  |  3KB
  1. Received: (from daemon@localhost)
  2.     by services.bunyip.com (8.8.5/8.8.5) id KAA27603
  3.     for urn-ietf-out; Wed, 4 Jun 1997 10:13:46 -0400 (EDT)
  4. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1])
  5.     by services.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA27596
  6.     for <urn-ietf@services.bunyip.com>; Wed, 4 Jun 1997 10:13:43 -0400 (EDT)
  7. Received: from beethoven.bunyip.com (beethoven.Bunyip.Com [192.197.208.5])
  8.     by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id KAA16803;
  9.     Wed, 4 Jun 1997 10:12:13 -0400 (EDT)
  10. Received: from localhost (leslie@localhost) by beethoven.bunyip.com (8.6.9/8.6.10) with SMTP id KAA05374; Wed, 4 Jun 1997 10:12:12 -0400
  11. X-Authentication-Warning: beethoven.bunyip.com: leslie owned process doing -bs
  12. Date: Wed, 4 Jun 1997 10:12:09 -0400 (EDT)
  13. From: Leslie Daigle <leslie@Bunyip.Com>
  14. To: harald.t.alvestrand@uninett.no, michaelm@rwhois.net,
  15.         "Ron Daniel, Jr." <rdaniel@lanl.gov>
  16. cc: urn-ietf@bunyip.com
  17. Subject: Re: [URN] URN resolution services question
  18. In-Reply-To: <3.0.32.19970603153026.00d58af0@cic-mail.lanl.gov>
  19. Message-ID: <Pine.SUN.3.95.970604100143.5288B-100000@beethoven.bunyip.com>
  20. MIME-Version: 1.0
  21. Content-Type: TEXT/PLAIN; charset=US-ASCII
  22. Sender: owner-urn-ietf@Bunyip.Com
  23. Precedence: bulk
  24. Reply-To: Leslie Daigle <leslie@Bunyip.Com>
  25. Errors-To: owner-urn-ietf@Bunyip.Com
  26.  
  27. On Tue, 3 Jun 1997, Ron Daniel, Jr. wrote:
  28.  
  29. > Harald, Leslie - any comments on redoing THTTP before it actually
  30. > appears as an RFC?
  31.  
  32. Yeah, Harald used Strong Terminology when we had some edits to the Syntax
  33. document.  Things are turning around off the RFC-editor plate pretty
  34. quickly these days, and it is _not_ appreciated when documents go through
  35. last call (and THTTP has gotten at least that far).
  36.  
  37. Unless there are different rules because this is an "experimental" RFC
  38. and not Standards Track (as the Syntax document was), I believe we
  39. have to wait until we have a document that is meant to "obsolete" the
  40. existing one.  I think there are better ways of handling this situation,
  41. just now.
  42.  
  43. Any comments, Harald?
  44.  
  45. Leslie.
  46.  
  47. ---------------------------------------------------------------------------
  48.  
  49.   "_Be_                                           Leslie Daigle
  50.              where  you                           
  51.                           _are_."                 Bunyip Information Systems
  52.                                                   (514) 875-8611
  53.                       -- ThinkingCat              leslie@bunyip.com
  54. ----------------------------------------------------------------------------
  55.